Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement: Update localheinz/json-normalizer #62

Merged
merged 1 commit into from
Apr 7, 2018

Conversation

localheinz
Copy link
Member

@localheinz localheinz commented Apr 7, 2018

This PR

  • updates localheinz/json-normalizer

Fixes #58.

💁‍♂️ For reference, see ergebnis/json-normalizer@0.5.2...0.6.0.

@localheinz localheinz force-pushed the feature/json-normalizer branch from 63abb9a to 8d08814 Compare April 7, 2018 08:06
@codecov
Copy link

codecov bot commented Apr 7, 2018

Codecov Report

Merging #62 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##             master    #62   +/-   ##
=======================================
  Coverage       100%   100%           
  Complexity       67     67           
=======================================
  Files             7      7           
  Lines           259    259           
=======================================
  Hits            259    259

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5ba125e...67ac6d0. Read the comment docs.

@localheinz localheinz force-pushed the feature/json-normalizer branch from 8d08814 to 17763c1 Compare April 7, 2018 08:07
@localheinz localheinz force-pushed the feature/json-normalizer branch from 17763c1 to 67ac6d0 Compare April 7, 2018 08:08
@localheinz localheinz merged commit 10632f2 into master Apr 7, 2018
@localheinz localheinz deleted the feature/json-normalizer branch April 7, 2018 08:23
@localheinz
Copy link
Member Author

Thank you, @xtreamwayz!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants